-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nixosTests.nixos-rebuild-specialisations: Fix #237069
nixosTests.nixos-rebuild-specialisations: Fix #237069
Conversation
@ofborg test nixos-rebuild-specialisations |
Fixed for linux, but why does it fail on arm? @RaitoBezarius is this also due to disk handling changes?
(see ofborg, https://github.com/NixOS/nixpkgs/pull/237069/checks?check_run_id=14158223935) |
stdenv | ||
sudo | ||
xorg.lndir | ||
system.includeBuildDependencies = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't this make the closure explode? :-(
I mean I dream of using this everywhere (while waiting for rebuildDependencyClosure which @JulienMalka is exploring).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not the build closure ;)
It balloons, but does not explode.
Right now the test itself explodes. Pieces everywhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So realistically I think our priorities should be
- maintainable tests
- working tests
- fast tests
This PR doesn't make (3) harder, because it's easy enough to find tests that do includeBuildDependencies = true
.
Meanwhile it fixes (1) and (2).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm on board with the "correct by design".
Looks like a bug/problem in GRUB installer script again, I think. But of course, my disk changes could have make this bug "visible" again. I assume the target for GRUB device should be |
Can't really dive into that now. |
Description of changes
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)